Network Computing with VOV


Shorten your design cycles by using all computing resources of your network!

Summary of features

  • VOV knows whant needs to be done
  • Supports networks with heterogeneous hardware and even a non-uniform name space for UNIX files
  • Supports concurrent overlapping requests, even from different designers, without executing any job more than once
  • Each job is dispatched to the best slave that offers all resources necessary to execute it
  • Load balancing and other rules of "netiquette"
  • Full job control capabilities: start, terminate, suspend, continue
  • The slave monitor shows the network activity
  • A picture of the slaves monitor

    Explanation

    A benefit of knowing completely and in detail all design dependencies is that VOV understands which jobs can be performed in parallel. In comparison with other load-sharing systems, VOV has the great advantage of knowing what needs to be done; in a sense, the task of distributing the jobs across the network becomes an easy one.

    Whenever a designer requests that a part of a design be brought up-to-date, (such operation being known as retracing), VOV schedules all necessary jobs and dispatches them to the available slaves.

    At the same time, other designers may request the retracing of other parts of the design. These multiple requests may in part or in whole overlap with existing requests, and VOV guarantees that no job will be executed more than once.

    Each slave is characterized by the resources it offers, by the relative power of the CPU, and by the load on its host, which can be updated every minute. The dispatching rule is that the longest job goes to the most powerful slave offering all required resources. The resources may include, for example, software licenses, amount of physical memory, access to special devices like printers and accelerators.

    The network may be heterogeneous in many ways. First, there may be machines from different vendors. VOV supports the equivalent of a parallel "make" for multiple architectures. A second source of heterogeneity comes from the many possible ways in which file systems may be mounted across the network. It is possible that the same file may have different names on different machines. VOV understand this and maps all names to a "logical canonical" name that is valid across the network.


    Back to index
    © Copyright 1996 Runtime Design Automation